Techniques for zero touch provisioning of edge nodes for a virtual private network by pushing configuration from a server

ABSTRACT

A method and apparatus for configuring a network interface to support a virtual private network includes storing configuration data at a server on a host computer on the provider network. It is determined without human intervention whether conditions are satisfied for sending the configuration data to a particular node at an edge of the provider network without receiving a request message from the particular node. If it is determined that conditions are satisfied, then the configuration data is sent to the particular node to cause the particular node to configure a particular interface for supporting a virtual private network over the provider network based on the configuration data. The particular node is different from the host. These techniques allow changes in configuration data to be pushed to provider edge nodes without human intervention.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit of Provisional Appln. 60/654,661, filed Feb. 19, 2005, the entire contents of which are hereby incorporated by reference as if fully set forth herein, under 35 U.S.C. §119(e).

This application claims benefit as a Continuation-in-part of Appln. Ser. No. ______ (Attorney Docket No. CIS001-0018), filed ______, ______ the entire contents of which are hereby incorporated by reference as if fully set forth herein, under 35 U.S.C. §120.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to establishing one or more virtual private networks (VPNs) using layer 2 protocols on a packet switching infrastructure that belongs to a trusted service provider; and in particular to pushing configuration data for each customer interface to a provider edge network node for VPN operation without human intervention.

2. Description of the Related Art

Networks of general purpose computer systems connected by external communication links are well known and widely used in commerce. The networks often include one or more network devices that facilitate the passage of information between the computer systems. A network node is a network device or computer system connected by the communication links.

Information is exchanged between network nodes according to one or more of many well known, new or still developing protocols. In this context, a “protocol” consists of a set of rules defining how the nodes interact with each other based on information sent over the communication links. The protocols are effective at different layers of operation within each node, from generating and receiving physical signals of various types, to selecting a link for transferring those signals, to the format of information indicated by those signals, to identifying which software application executing on a computer system sends or receives the information. The conceptually different layers of protocols for exchanging information over a network are described in the Open Systems Interconnection (OSI) Reference Model. The OSI Reference Model is generally described in more detail in Section 1.1 of the reference book entitled Interconnections Second Edition, by Radia Perlman, published September 1999, which is hereby incorporated by reference as though fully set forth herein.

Communications between nodes are typically effected by exchanging discrete packets of data. Each packet typically comprises 1] header information associated with a particular protocol, and 2] payload information that follows the header information and contains information that may be processed independently of that particular protocol. In some protocols, the packet includes 3] trailer information following the payload and indicating the end of the payload information. The header includes information such as the source of the packet, its destination, the length of the payload, and other properties used by the protocol. Often, the data in the payload for the particular protocol includes a header and payload for a different protocol associated with a different, usually higher layer of the OSI Reference Model. The header for a particular protocol typically indicates a type for the next protocol contained in its payload. The payload protocol is said to be encapsulated in the header protocol. The headers included in a packet traversing multiple heterogeneous networks, such as the Internet, typically include a physical (layer 1) header, a data-link (layer 2) header, an internetwork (layer 3) header and a transport (layer 4) header, as defined by the Open Systems Interconnection (OSI) Reference Model.

The layer 2 tunneling protocol (L2TP) is a link layer (layer 2) protocol established to provide a persistent virtual circuit as a tunnel between two end nodes of a trusted sub-network. In network parlance, a tunnel for data is simply a protocol that encapsulates that data. The persistent tunnel, or virtual circuit on a packet switched network is often called a pseudo-wire. L2TP facilitates the tunneling of point to point protocol (PPP) packets across an intervening network in a way that is as transparent as possible to both end-users and applications. Using L2TP tunneling, an Internet Service Provider (ISP), or other access service, can create a pseudo wire to link customer's remote sites or remote users with corporate home networks. More recent versions of L2TP facilitates tunneling of a number of data link types, including, but not limited to, Point to Point Protocol (PPP), Frame Relay (FR), Asynchronous Transfer Mode (ATM), High Level Data Link Control (HDLC) and Ethernet. L2TP is described at the time of this writing in Internet Engineering Task Force (IETF) request for comments (RFC) 2661 which can be found in a file named rfc2661. txt, which can be found, along with other RFC files, at the world wide web domain www.ietf.org in the file directory named rfc. L2TPv3 is described in RFC 3817 available in file rfc3817.txt in the same directory. The entire contents of RFC 2661 and RFC 3817 are hereby incorporated by reference as if fully set forth herein.

Some protocols follow a layer 2 protocol and precede a layer 3 protocol; and are said to be layer 2.5 protocols. For example, the multi-protocol layer switch (MPLS) is a layer 2.5 protocol that provides for the designation, routing, forwarding and switching of traffic flows through a network; and supports the transfer of multiple data link (layer 2) types. MPLS is described at the time of this writing in IETF RFC 3031 and RFC 3032 which can be found in files named rfc3031.txt and rfc3031.tx, respectively, the entire contents of which are hereby incorporated by reference as if fully set forth herein.

A virtual private network (VPN) is a technology to logically separate the data packets traveling over the same physical network, so that a user of one VPN does not see the data communicated between users of a: different VPN. ISPs frequently offer to customers VPNs that are implemented as one or more pseudo wires on a packet switched network (PSN) infrastructure, such as a network of routers using the Internet Protocol (IP) as a layer 3 protocol or using MPLS as a layer 2.5 protocol. A common approach for providing the tunneling functions for a VPN is to use the layer 2 tunneling of L2TPv3 as a payload in IP data packets. In some approaches, a protocol for Any Transport over MPLS (AToM) available from CISCO SYSTEMS™, Inc. of San Jose Calif. is used to support layer 2 tunneling in a payload in MPLS data packets. Then layer 2 protocols, such as PPP, FR, ATM, HDLC, Ethernet are used to transmit customer data for a VPN.

A customer contracts with an ISP to provide a VPN among customer sites and to support certain kinds and amounts of data traffic over that VPN. In response, the ISP configures interfaces to customer equipment on several intermediate network nodes at the edge of an ISP network (so-called “provider edge nodes,” PE, or simply “edge nodes”). Each interface is configured to communicate the type of traffic designated for that interface and encapsulate it in one or more tunnels, each tunnel directed to one or more other interfaces on other edge nodes of the ISP network. In the parlance of this technology, configuring each affected interface on each affected edge node provisions the VPN.

A PE interface to customer equipment (CE) is called an attachment circuit (AC) or port. Each physical interface can support one or more logical attachment circuits. For example, a single physical interface for ATM traffic can support multiple ATM virtual circuits, which may be directed to different VPNs; each ATM virtual circuit is considered a different AC to be configured. Configuration data specifies values for one or more parameters for each attachment circuit (AC). The parameters and values depend on the layer 2 protocol to be supported in the VPN, the topology of the VPN, and the tunneling protocol used to establish the pseudo wires. Example configuration data for a logical ATM AC specifies a percentage of total bandwidth devoted to the logical AC, a cell-packing value, the other PE devices in the topology, and a control plane protocol to establish and maintain pseudo wires among the connected PE.

Currently, provisioning the VPN is a manual process, in which a network administrator determines which data packets on each interface are sent out on which link to the provider network using which designations to be recognized by subsequent intermediate nodes and edge node as a separate tunnel. The manual provisioning process is tedious and error prone. Furthermore, when a new piece of customer equipment is connected to an edge node, that equipment is unable to communicate over the VPN unless and until the human administrator provisions the VPN to add the new interface. Thus the process is subject to delays. The delays grow in severity as the human administrator becomes busier. The tedium and propensity for error increase with the complexity of the VPN topology (e.g., as the numbers of interfaces and edge nodes increase).

Furthermore, when a new piece of equipment is connected to an edge node, the configuration data at several provider edge nodes may change. Typically, the network administrator causes configuration data or configuration commands to be sent to each affected node for all interfaces, even though many of those interfaces are unchanged.

Based on the foregoing description, there is a clear need for techniques to provision a VPN on a provider's network without the deficiencies of prior art approaches. In particular, there is a clear need for techniques to provision a VPN on a provider's network without human intervention whenever there is a change to a VPN.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1A is a block diagram that illustrates a virtual private network on a provider packet-switched network for a virtual private wire service, according to an embodiment;

FIG. 1B is a block diagram that illustrates a virtual private network on a provider packet-switched network for a virtual private LAN service, according to an embodiment;

FIG. 2 is a flow diagram that illustrates at a high level a method for pushing configuration data for a virtual private network from a server distinct from a provider edge node, according to an embodiment;

FIG. 3A is a block diagram that illustrates a customer interface record 300 on a provisioning server, according to an embodiment;

FIG. 3B is a block diagram that illustrates a VPN record 320 on a provisioning server, according to an embodiment;

FIG. 3C is a block diagram that illustrates a pseudo wire record 340 on a provisioning server, according to an embodiment;

FIG. 3D is a block diagram that illustrates a combined VPN record 360 on a provisioning server, according to an embodiment; and

FIG. 4 is a block diagram that illustrates a computer system upon which an embodiment of the invention may be implemented.

DETAILED DESCRIPTION

A method and apparatus are described for zero touch provisioning of edge nodes for virtual private networks. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.

Certain embodiments of the invention are described in the context of a single server on a host of a provider network away from the provider edge, which provisions a single, layer-two virtual private network (VPN) on an Internet Protocol (IP) infrastructure for a single customer; but the invention is not limited to this context. In other embodiments, one or more servers on hosts at or away from the provider edge provision one or more layer-two VPNs for one or more customers using one or more protocols on a packet switching network based on one or more protocols above layer 2, such as IP and multi-protocol layer switch (MPLS) protocol.

The client-server model of computer process interaction is widely known and used in commerce. According to the client-server model, a client process sends a message including a request to a server process, and the server process responds by providing a service. The server process may also return a message with a response to the client process. Often the client process and server process execute on different computer devices, called hosts, and communicate via a network using one or more protocols for network communications. The term “server” is conventionally used to refer to the process that provides the service, or the host computer on which the process operates. Similarly, the term “client” is conventionally used to refer to the process that makes the request, or the host computer on which the process operates. As used herein, the terms “client” and “server” refer to the processes, rather than the host computers, unless otherwise clear from the context. In addition, the process performed by a server can be broken up to run as multiple servers on multiple hosts (sometimes called tiers) for reasons that include reliability, scalability, and redundancy, but not limited to those reasons.

1.0 Example Virtual Private Network

FIG. 1A is a block diagram that illustrates a virtual private network 100 based on a virtual private wire service (VPWS) on a provider packet-switched network (PSN) 110, according to an embodiment. The provider PSN 110 includes two or more provider edge nodes, e.g., PE 120 a, 120 b, 120 c (collectively referenced hereinafter as PE 120). Each PE 120 includes one or more physical interfaces to which customer premises equipment (CE) may be connected. The physical interfaces support one or more physical or logical attachment circuits (ACs) used by the customer to communicate over network 110. For example, PE 120 a includes ACs 122 a, 122 b, 122 c, 122 d, 122 e. CE 150 a is connected to PE 120 a through ACs 122 a, 122 b; and CE 150 b is connected to PE 120 a through ACs 122 c, 122 d. AC 122 e is available for connecting to CE, but no CE is currently connected. Similarly, CE 150 c is connected to PE 120 b through ACs 122 f, 122 g, 122 h. CE 150 d is connected to PE 120 c through ACs 122 i, 122 j, 122 k. The CEs 150 a, 150 b, 150 c, 150 d are collectively referenced hereinafter as CEs 150. The ACs 122 a, 122 b, 122 c, 122 d, 122 e, 122 f, 122 g, 122 h, 122 i, 122 j, 122 k are collectively referenced hereinafter as ACs 122. Also shown is server 130 on PSN 110.

VPN 100 includes multiple tunnels between pairs of PEs. Each such tunnel is called a virtual circuit or pseudo wire (PW). FIG. IA depicts five PWs, 140 a, 140 b, 140 c, 140 d, 140 e (collectively referenced hereinafter as PWs 140) used to provide VPWS for point to point traffic among CEs 150. Point-to-point data packet traffic between CE 150 a and CE 150 d is carried by AC 122 a and PW 140 a and AC 122 k. Point-to-point data packet traffic between CE 150 b and CE 150 d is carried by AC 122 c and PW 140 b and AC 122 j. Similarly, point-to-point data packet traffic between CE 150 a and CE 150 c is carried by AC 122 b and PW 140 c and AC 122 h; and such data packet traffic between CE 150 b and CE 150 c is carried by AC 122 d and PW 140 d and AC 122 g. Point-to-point data packet traffic between CE 150 c and CE 150 d is carried by AC 122 f and PW 140 e and AC 122 i. In some embodiments, one or more ACs 122 are logical ACs that share the same physical wire; e.g., ACs 122 a, 122 b are logical ACs that share the same physical transmission medium from edge node 120 a to CE 150 a. For example, FR, ATM and Ethernet virtual local area networks (VLANs) are logical attachment circuits which allow multiple customers (or services) to be transported on the same physical wire.

This complete collection of PWs in FIG. 1A is called a full mesh. In some circumstances, such a full mesh involves more PWs and associated costs than are needed. For example, if customer needs are satisfied so long as CE 150 d has a PW to CE 150 b and CE 150 c has a PW to CE 150 a, then only two PWs are needed, e.g., 140 a and 140 c, with fewer associated attachment circuits including only 122 j, 122 c and 122 h, 122 b.

In some VPN service, called a virtual private local-area network (LAN) service (VPLS) every CE is connected to every other CE on the VPN and data traffic flows to then all as if on an Ethernet LAN. FIG. 1B is a block diagram that illustrates a virtual private network 101 on a provider packet-switched network 110 for VPLS, according to an embodiment. For example, VPN 101 includes sufficient PWs 140 f, 140 g, 140 h to connect each PE 120 a, 120 b, 120 c to the others. Traffic between different CEs on the VLAN is not distinguished by separate ACs and separate PWs. Thus, CEs 150 a, 150 b are on the same LAN, which forms AC 122 l, and traffic from both is carried to CE 150 c via a single PW 140 g to PE 120 b and thence via a single AC 122 m. Similarly, traffic from both is carried to CE 150 d via a single PW 140 f to PE 120 c and thence via a single AC 122 n. Inactive AC 122 e is kept separate for use in a different VPLS or VPWS VPN. Clearly, the provisioning of PSN 110 is different for the different VPNs 100 and 101, even though both involve the same PEs and CEs.

2.0 Method at Server for Provisioning a VPN

According to various embodiments of the invention, one or more servers on the provider network store and push configuration data to provider edge nodes to provision one or more VPNs without further human intervention. For example, provisioning server 130 stores and automatically pushes configuration data to PE 120 a to switch traffic for AC 122 a with PW 140 a, AC 122 b with PW 140 c, AC 122 c with PW 140 b, and AC 122 d with PW 140 d. Similarly, provisioning server 130 stores and automatically pushes configuration data to PE 120 b and PE 120 c. Even with the relatively simple topology of FIG. 1A, the danger of errors during manual configuration is high.

According to some embodiments, server 130 also stores configuration data for unused AC 122 e. When a new CE (not shown) or service is connected to AC 122 e, server 130 automatically pushes the configuration data to PE 120 a and causes new PWs (not shown) to be formed with PE 120 b or PE 120 c or both. Similarly server 130 automatically pushes configuration data to PEs 120 b, 120 c that cause those PEs to switch the new PWs with new ACs (not shown) on PEs 120 b, 120 c. Thus server 130 pushes configuration data without human intervention for provisioning VPN 100. If AC 122 e joins VPN 101, instead of joining VPN 100, then server 130 causes PE 120 a to merge AC 122 e with LAN AC 122 l and sends traffic from AC 122 e over both extant PWs 140 a, 140 c.

FIG. 2 is a flow diagram that illustrates at a high level a method 202 for provisioning a virtual private network at a server distinct from a provider edge node, according to an embodiment. Although steps are shown in FIG. 2 in a particular order for purposes of illustration, in other embodiments one or more steps may be performed in a different order or overlapping in time or omitted, or changed in some combination of ways.

During step 210, configuration data is received at the server and stored. The configuration data indicates values for one or more parameters relevant to configuring one or more attachment circuits to participate in one or more virtual private networks over the provider packet switched network. Any method may be used to receive this configuration data. In some embodiments, the configuration data is input manually by a network administrator and stored locally or on a remote node. In some embodiments, the data is retrieved from storage locally or remotely. In some embodiments, the data is sent in a message from another node on the network either in response to a message from the peer requesting the data or in an unsolicited message. In some embodiments a combination of different methods is used.

Often, the configuration data is derived based on customer specifications for the topology for the VPN and level of surface obtained when the customer subscribes to the service. For example, configuration data is received and stored at server 130 that indicates for VPN 100 the service is VPWS, the attachment circuits 122 are frame relay virtual circuits, each identified by a data link connection identifier (DLCI), the participating edge nodes are PEs 120 a, 120 b, 120 c, and PWs 140 a, 140 b, 140 c, 140 d, 140 e have a certain level of service, e.g., a certain value for a per-hop behavior (PHB) parameter. The use of PHB to indicate level of service is described in RFC 3140 entitled “Per Hop Behavior Identification Codes,” by D. Black, S. Brim, B. Carpenter, F. Le Faucheur (June 2001), the entire contents of which are hereby incorporated by reference as if fully set forth herein.

In an alternative example, configuration data is received and stored at server 130 that indicates for VPN 100 the service is VPWS, the attachment circuits 122 b, 122 c, 122 h, 122 j are ATM virtual circuits, the participating edge nodes 120 are PEs 120 a, 120 b, 120 c, with connecting pseudo wires PW 140 b and PW 140 c that are built on MPLS and have a level of service indicated by a value of an MPLS experimental (EXP) parameter. The use of EXP to indicate level of service is described in RFC 3032 entitled “MPLS Label Stack Encoding” by E. Rosen, D. Tappan, G. Fedorkow, Y. Rekhter, D. Farinacci, T. Li, A. Conta, (January 2001), the entire contents of which are hereby incorporated by reference as if fully set forth herein. RFC 3032 and RFC 3140 are implementations of Differentiated Services Code Point (DSCP) described in RFC 2474 entitled “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers,” by K. Nichols, S. Blake, F. Baker, D. Black (December 1998), the entire contents of which are hereby incorporated by reference as if fully set forth herein.

During step 222, data about the state of the network is received; but not from a particular provider edge node to be configured. The network state data may be received in any other manner, such as described above for the configuration data. In some embodiments, the state data is received from a human administrator who indicates that one or more interfaces on a PE should be configured immediately.

In preferred embodiments, the data about the state of the network is received automatically without human intervention. For example, the configuration data indicates that a particular interface, customer equipment or provider edge node is to join a VPN at a particular time, and the state data simply indicates the current time. In some embodiments, the server polls one or more nodes on the provider packet-switched network 110 during step 222 to determine the current state of the network. In some embodiments, a message is received from a device, other than the provider edge node to be configured, that configuration data should be sent to that provider edge node. For example, the server 130 receives from some other device a simple network management protocol (SNMP) set command to send configuration data to PE 120 c.

In some embodiments, step 222 includes determining the current set of equipment involved in the virtual private network, including customer premises equipment, provider edge nodes, and other nodes in the provider network.

In some embodiments, step 222 includes determining the set of parameters associated with each category of service. For example, some virtual private network service providers allow customers to form pseudo wires that support one of three levels of service: gold, silver, and bronze. Each level has a different combination of quality of service parameters that are guaranteed along the pseudo wire, such as minimum bandwidth, maximum latency, maximum jitter, and support for voice or other media delivery services. The parameter values associated with these levels of service may change from time to time, for example, in response to customer demands and improvement to the underlying infrastructure of the packet switched network 110. Step 222 includes detecting changes in the parameter values associated with these levels of service. For example, in some embodiments, a human administrator updates the data stored at provisioning server 130, and a background task detects the change. In some embodiments, a human administrator updates the definition of a level of service at some other device or server, and provisioning server 130 is notified of the change by the other server or periodically checks the definitions at that other server by sending a request to that other server.

In step 232, it is determined whether conditions in the network are satisfied to send configuration data to one or more of the provider edge nodes, e.g., PEs 120, based on the data received in step 222. Any conditions may be used to determine when to send the configuration data to the edge nodes. In some embodiments, the current state data is compared against stored state data, and the condition is satisfied when the current state matches the stored state. In some embodiments, the condition is satisfied when a certain message is received from a human administrator, or from a different server, or network device. For example, in some embodiments, a customer subscribes to a VPN service on the provider's public web site, and the conditions are satisfied when the web site server sends a message to the configuration server 130 to activate the service. In some embodiments, the web server sends a SNMP set command to the provisioning server 130, to indicate when conditions are satisfied for sending configuration data to a provider edge node.

In some embodiments, the conditions are satisfied when a piece of equipment, other than the particular edge node to be configured, joins or leaves the set that support the VPN, for example, when the VPN is extended to include a new provider edge node. In some embodiments, the conditions are satisfied when a parameter associated with a level of service changes, e.g., when the minimum bandwidth associated with the gold level of service increases.

In a preferred embodiment, step 232 is performed without human intervention.

In step 240, the configuration server pushes configuration data to the provider edge node so that the provider edge node can configure the customer interface without human intervention to send data over the VPN. Thus a human administrator does not touch the provider edge node at the time it is configured to connect an attachment circuit to a VPN. This is called zero touch provisioning.

For example, when the provisioning server 130 receives a SNMP set command to send configuration data to PE 120 c, provisioning server 130 responds by sending configuration data to PE 120 c. For purposes of illustration, it is assumed that the configuration data indicates VPWS for VPN 100 with an ATM virtual circuit as attachment circuit 122 j, switching cells on that virtual circuit with a PW to PE 120 a, and certain properties for the PW 140 b formed.

In a VPLS, the PW (e.g., 140 f) is likely already established. If the PW is not already established, the PW is set up by having the configuration receiving PE (e.g., PE 120 c) send an advertisement to the remote PE (e.g., PE 120 a), indicating at least an identifier for the set of PEs that make up the VPN. The remote PE (e.g., PE 120 a) can receive further details about that set of PWs from the provisioning server (e.g., server 130), to complete configuration at the remote PE. Using single-sided signaling, the advertisement includes all the data used by the remote PE, so that the remote PE does not need to receive additional configuration data from the provisioning server.

There are several advantages of the method 202 compared to the prior art practice. One obvious advantage is that a human administrator is not required at the time the conditions are satisfied for doing the configuring. The provisioning information is prepared ahead of time when it is stored on the server and when there is less time pressure and less chance of error. There is also less delay, because the configuration information is available automatically as soon as conditions are satisfied, without having to wait for a human in the process. Also, when a provider edge node is replaced, its configuration data is still available on the server.

By the same token, repeated configuration of the same attachment circuits are accommodated without any additional effort. For example, if the physical interface carrying logical attachment circuits 122 i, 122 j, 122 k needs to be replaced, the information to configure it is already available on the server. The new physical interface is placed in PE 120 c, and the server 130 sends the configuration data appropriate for it. Without further human intervention, the PE 120 c uses the configuration data sent by the server 130 to configure the three logical attachment circuits and their associations with PWs 140 a, 140 b, 140 e, respectively. Under prior art practice, the human administrator would have to be involved to manually configure the new interface, either locally or at a remote management tool server and force the new configuration data down to the affected edge nodes.

Another advantage is that, in some embodiments, only the configuration data for less than all interfaces are sent to the PE 120. For example, if CE 150 b and CE 150 c are not yet connected to PE 120 a and 120 b, respectively, then the configuration data sent to PE 120 c is only for AC 122 k to PW 140 a to PE 120 a. The configuration data for the other ACs 122 i, 122 j are not sent and not processed at the PE 120 c. This saves both memory and computational resources at PE 120 c and the network bandwidth that would be consumed to send the additional configuration data.

In some embodiments, only the changed configuration data is sent. For example, when CE 150 c joins VPN 100, only the configuration data for AC 122 i and PW 140 e to PE 120 b is sent to PE 120 c. This is an advantage over a prior approach in which a large block of commands for configuring every customer interface is sent whenever there is any change. The prior art approach would send configuration data for not only the new AC 122 i, but also for the AC 122 j that PE 120 c already has. The prior art approach thus consumes extra network bandwidth in transmitting the configuration data already in the possession of the receiving node. Furthermore, the prior approach also consumes extra processor resources on the receiving edge node as it causes the receiving edge node to either reconfigure the attachment circuit that is already operating or parses the commands to avoid reconfiguring that attachment circuit. Furthermore, as the extra processing is done, resources are diverted from processing traffic on the attachment circuit. Reconfiguring an attachment circuit that is already functioning reduces the availability of that attachment circuit. Thus, at least some embodiments of the present invention reduce network traffic, increase processing power at a provider edge node, and increase availability of attachment circuits.

One prior approach uses a RADIUS server to store data indicating all the provider edge nodes on a given VPN. While the list of other provider edge nodes on a VPN is part of configuration data, providing only this information does not, by itself, alleviate the involvement of a human administrator. In the prior approach, the human administrator still touches each provider edge node to configure it as a member of the VPN, and associate the VPN with one or more attachment circuits, and to indicate the type of pseudo wire properties to use. Each provider edge node then sends a message to the RADIUS server to indicate that provider edge node's membership in the VPN, and to request the names of the other provider edge nodes currently members of the VPN. In some embodiments of this approach, the RADIUS server polls each provider edge node to determine the VPN memberships as set on the provider edge by the human administrator.

In other prior art approaches, a manufacturer-specific command language (e.g., the command line instructions, CLI, of Cisco Systems Inc., San Jose, Calif.) is used to configure attachment circuits for a VPN based on input by a human administrator. In some embodiments of the present invention, an open protocol is used to communicate between provisioning server 130 and provider edge nodes, e.g., PEs 120. An advantage of using an open protocol is that open protocol servers are widely deployed and supported. For example, in some embodiments the simple network management protocol (SNMP) is used to exchange messages with both provider edge nodes and server 130. In some embodiments, server 130 is a Network Management Server (NMS) that is used or modified to handle the configuration data with SNMP. Other open protocols and corresponding or modified servers may be used to send some or all configuration data between provisioning server (e.g., server 130) and provide edge nodes (e.g., PE 120), including but not limited to the Border Gateway Protocol (BGP), the Label Distribution Protocol (LDP), the generic attribute registration protocol (GARP) virtual local area network (VLAN) Registration Protocol (GVRP), and the Resource Reservation Protocol (RSVP).

In some embodiments described in more detail in the next section, the Remote Authentication Dial In User Service (RADIUS) protocol is used to communicate configuration data; and a RADIUS server is used or modified to perform some or all of the functions at provisioning server 130 or provider edge node 120, or both.

3.0 Radius Server for Pushing VPN Provisionsing

In this section, the use of the RADIUS protocol for communicating between the provisioning server 130 and a provider edge node 120 is described. RADIUS is well known and widely used in the art; and is described in RFC2865 and RFC 3576, the entire contents of each of which are hereby incorporated by reference as if fully set forth herein. In the case in which a CE belongs to a foreign VPN of another provider, the RADIUS server of the local provider acts as a proxy client to a RADIUS server of the foreign provider.

There are several advantages to using a RADIUS server. RADIUS servers are already widely deployed on a large number of provider packet-switched networks. The RADIUS protocol allows for the definition of new attributes that can be defined to hold configuration data, as described in the following. RADIUS is designed to give prescribed responses to prescribed requests, as is needed to return prescribed configuration data for requests. The RADIUS protocol also allows for the definition of vendor-specific attributes that can be defined to hold configuration data. RADIUS has recently been extended to support an on-demand push model, so that network state can be determined by any process, which can then prompt the RADIUS server to push configuration data to a PE. Furthermore, the RADIUS protocol does not preclude adding additional functionality to a RADIUS server, as long as the necessary functions are performed.

In an illustrated embodiment of the invention, a RADIUS server is used as a provisioning server 130 to push configuration data to provision one or more VPNs. In this embodiment, an AC identifier (AC ID) is associated with a virtual circuit identifier (VC ID) that indicates a collection of one or more pseudo wires in a VPN. The VC ID is associated, in turn, with one or more other PEs 120, and associated with one or more PWs 140. Thus hierarchical relationships among VPNs, PEs, PWs, and ACs are stored in the flat files of RADIUS records. In an example embodiment, configuration data is stored by a RADIUS server during step 210 when a customer first contracts for service.

When particular conditions are satisfied, as determined in step 232, configuration data is pushed to the edge node automatically, without human intervention. For example, when a set command is received with the AC ID at a RADIUS server, the RADIUS server pushes associated VC ID or PW properties or both. As another example, on a particular date when contracted services are scheduled to begin, the RADIUS server pushes the configuration data to the affected edge nodes.

Based on the AC ID in the configuration data sent by the RADIUS server, the receiving edge node determines how to switch and encapsulate traffic on the associated AC into one or more tunnels (PWs) associated with a particular VPN. Thus substantial delays are avoided between a time that a customer contracts for services (or customer premises equipment is connected to an edge node) and a time when the associated VPN can be used.

Example data structures for storing configuration data on a RADIUS server are illustrated in FIGS. 3A, 3B, 3C, and 3D. Some or all of these data structures may be used in other embodiments of provisioning server 130 that do not use the RADIUS protocol, or on the provider edge node after the configuration data is delivered. FIG. 3A is a block diagram that illustrates a customer interface record 300 on a provisioning server, according to an embodiment. In the illustrated embodiment, the record 300 includes four fields, a router identification (Router ID) field 302, an attachment circuit identification (AC ID) field 304, a VC identification (VC ID) field 306, and an attachment circuit (AC) service field 308.

The Router ID field 302 holds data that uniquely indicates a provider edge node that is to receive the configuration data. The value of the Router ID field 302 serves as an index to a particular record in the data stored on the RADIUS server. In an illustrated embodiment, the value of the Router ID field is the IP address of the provider edge node on the provider network. An IP address is four octets that are commonly designated by four decimal values separate by three dots, where each decimal value falls between 0 and 255, inclusive. For purposes of illustration, it is assumed that PEs 120 a, 120 b, 120 c have IP addresses 1.1.1.1, 1.1.1.2 and 1.1.1.3, respectively. Thus, in some embodiments, the Router ID field 302 holds the IP address of the provider edge node (e.g., PE120 a) to be configured. In some embodiments, the Router ID field holds other data, such as text, that uniquely identifies the provider edge node (e.g., PE 120 a) in the provider network, or any kind of network address, such as a VPNv4 IP address or an IPv6 address.

According to a particular embodiment, a PE-Router-ID attribute is added to the RADIUS attributes of RFC2865. The PE-Router-ID attribute includes a first octet (eight bits) that indicates the type is a PE-Router-ID, a second octet that indicate the length of the attribute is six octets, and four octets that hold the value, e.g., the IP address or an arbitrary number assigned by the owner of the ID space. In this embodiment, the Router ID field 302 holds the PE-Router-ID attribute. For example, the value of PE-Router-ID for PE 120 a is given by the six octets X.6.1.1.1.1, where the octet value “X” indicates the type is a PE-Router-ID and is assigned by agreement of the RADIUS protocol authority or as a vendor-specific attribute.

According to a particular embodiment, a PE-Address attribute is also added to the RADIUS attributes of RFC2865. The PE-Address attribute includes a first octet that indicates the type is a PE-Address, a second octet that indicates the length of the attribute is six octets, and four octets that hold the IP address. In some embodiments, the Router ID field 302 holds the PE-Address attribute. For example, the value of PE-Router-ID for PE 120 a is given by the six octets Y.6.1.1.1.1, where the octet value “Y” indicates the type is a PE-Address and is assigned by agreement of the RADIUS protocol authority or as a vendor-specific attribute.

In some embodiments, the Router ID field 302 holds either the RADIUS PE-Address attribute or the RADIUS PE-Router-ID, as can be determined by the type in the first octet.

The AC ID field 304 holds data that indicates a physical or logical attachment circuit on a provider edge node that is a member of a VPN. The value of the AC ID field 304 serves as a secondary index to a particular record in the data stored on the RADIUS server. Any method may be used to indicate the attachment circuit. In one embodiment, the AC ID field 304 holds data that uniquely indicates a physical link on the router identified in Router ID field 302. For example, a certain class of routers internally number the physical interfaces on each router form 0 through N-1, where N is the number of physical interfaces. In some embodiments the physical interfaces are named in software. In some embodiments, the AC is uniquely indicated by an arbitrary value (e.g., a name or number).

In some embodiments, the AC ID is based on a logical attachment circuit, such as a frame relay or ATM virtual circuit name, used on the CE. For example, ATM virtual circuits are identified by an ATM port name, a one-octet virtual path identifier (VPI) that indicates a group of virtual circuits, and a two-octet virtual channel identifier (VCI) in the header of a ATM cell. The VPI/VCI combination is used to identify the next destination of an ATM cell as it passes through a series of ATM switches. In embodiments using the ATM virtual circuit identifier as an arbitrary name for an attachment circuit, the AC ID comprises the ATM port, VPI and VCI. For example, if the ATM port is named “atm 1/0” and the VPI is “2” and the VCI is “34,” then an appropriate AC ID is “atm1/0.2.34.” Since the customer subscribes to the VPN, the customer names for the virtual circuits are appropriate to use as an index into the configuration data stored on the RADIUS server.

In some embodiments, the AC ID field 304 holds CE ID data that uniquely identifies a piece of customer premises equipment connected to provider edge equipment. For example, a network access identifier (NAI) or a Domain Name Server (DNS) host name associated with the CE can serve as CE ID data. The use of NAI to indicate a CE is described in RFC 2486 entitled “The Network Access Identifier,” by B. Aboba, M. Beadles (January 1999), the entire contents of which are hereby incorporated by reference as if fully set forth herein. The use of DNS to indicate a CE is described in RFC 1101 entitled “DNS encoding of network names and other types,” by P. V. Mockapetris (April 1989), the entire contents of which are hereby incorporated by reference as if fully set forth herein. It is assumed for purposes of illustration that CE 150 d has an NAI of “providerX/atlanta@vpnY.domainZ.net.” For VPLS or for a CE with a single attachment circuit to a provider edge node, an AC ID value that is only a CE ID value is sufficient to determine VPN membership. For VPWS and a CE with multiple logical or physical attachment circuits to a provider edge, an AC ID includes both a CE ID along with a customer name for an attachment circuit to determine a unique identifier for an attachment circuit, and thence VPN membership.

In some embodiments, the AC ID field 304 holds either an AC specific identifier or a CE identifier.

The VC ID field 306 holds data that uniquely indicates a particular collections of pseudo wires on the provider network, e.g., network 110. In a VPLS, the VC ID indicates all the pseudo wires in the VPN, e.g., PWs 140 f, 140 g, 140 h in VPN 101. In a VPWS, the VC ID indicates a single pseudo wire that provides point-to-point traffic as part of a particular VPN. In some embodiments, the VC ID field 306 holds data that indicates a VPN-ID as described in RFC2685, the entire contents of which are hereby incorporated by references as if fully set forth herein.

According to a particular embodiment, a VPN-ID attribute is added to the RADIUS attributes of RFC2865. The VPN-ID attribute includes a first octet that indicates the type is a VPN-ID, a second octet that indicate the length of the attribute, and the length minus two (length-2) octets that hold text that indicates the value. The text is composed of two colon separated parts: a VPN authority, organizationally-unique identifier, and a VPN index number within the organization.

In some embodiments the VC ID field 306 holds data that indicates a VPN differently from the VPN-ID as described in RFC2685. According to a particular embodiment, a Router-Distinguisher attribute is added to the RADIUS attributes of RFC2865 as an alternative to the VPN-ID for a VC ID. The Router-Distinguisher attribute includes a first octet that indicates the type is a Router-Distinguisher, a second octet that indicate the length of the attribute, and length-2 octets that hold text that indicates the value. The text is composed of three colon separated parts: a distinguisher type, an administrator identifier, and an assigned number. If the distinguisher type is “0”, the administrator identifier contains a two-octet Autonomous System Number (ASN) defined by an Internetwork Autonomous Number authority, and the assigned number is a four-octet value assigned by the enterprise responsible for the ASN. As an example of this type, the text “0:114:23” indicates the administrator ANS is 114, and that administrator assigns a number 23 to the VC of interest. If the distinguisher type is “2”, the administrator identifier contains a four-octet ASN, and the assigned number is a two-octet value assigned by the enterprise responsible for the ASN. As an example of this type, the text “2:70000:216” indicates the administrator ANS is 70000, and that administrator assigns a number 216 to the VC of interest. This is similar to distinguisher type 0, but with octets moved from the assigned number to the administrator identifier. If the distinguisher type is “1”, the administrator identifier contains a four-octet IP address, and the assigned number is a two-octet value assigned by the enterprise controlling the IP address space. As an example of this type, the text “1:1.2.3.4:10001” indicates the administrator for the VPN name is at node 1.2.3.4, and that administrator assigns a number 10001 to the VC of interest.

In some embodiments, the VC ID field 306 holds either the RADIUS VPN-ID attribute or the RADIUS Router-Distinguisher attribute, as can be determined by the type in the first octet. In some embodiments, the VC ID serves as an attachment group identifier (AGI) so that each attachment circuit on a VPN can be uniquely identified within the group identifier using an attachment individual identifier (AII).

The AC Service field 308 holds data that describes the service to be provided to an AC or CE. In some embodiments, the field 308 includes data that indicates the type of service, e.g., whether the service type is VPLS, VPWS, or IP-only LAN-like Service (IPLS) or some other type of service. In some embodiments, the field 308 includes data that indicates attachment circuit specific parameters. Attachment circuit-specific parameter include, but are not limited to: a quality of service level associated with minimum values for bandwidth, and maximum values for latency and jitter; specific values for bandwidth, latency and jitter; an attachment circuit data plane protocol and control plane protocol; authentication credentials; attachment circuit original equipment manufacturer (OEM) signaling; and values for configurable parameters associated with those protocols, such as cell packing for ATM, maximum transmission unit (MTU) for packet sizes. For purposes of illustration, it is assumed that AC Service field 308 holds data that indicates a service type of VPWS with ATM protocol for both data and control planes on the attachment circuits, each attachment circuit allowed up to 40% of bandwidth on a physical interface, and a cell packing value of 1.

FIG. 3B is a block diagram that illustrates a VPN record 320 on a provisioning server, according to an embodiment. In the illustrated embodiment, the record 320 includes three fields, a Router ID field 302, VC ID field 306, and an Other PE list field 324.

The Router ID field 302 and VC ID field 306 are as described above for the attachment circuit record 300. The value of the Router ID field 302 serves as a primary index, and the value of the VC ID field serves as a secondary index, to a particular VPN record 320 in the data stored on the RADIUS server.

The Other PE list field 324 holds data that indicates one or more provider edge nodes to which the edge node identified in Router ID field 302 forms pseudo wires to support the VC indicated in the VC ID field 306. For VPWS, the Other PE list 324 includes an identifier for a single PE different from the PE indicated by the Router ID field 302. In the example VPWS, VPN 100, the Other PE list field 324 for the record with Router ID value 1.1.1.1 (PE 120 a) and VC ID corresponding to PW 140 a holds data that indicates PE 120 c. In the same example, the Other PE list field 324 for the record with Router ID value 1.1.1.3 (PE 120 c) holds data that indicates PE 120 a. For VPLS, the Other PE list 324 includes identifiers for all PEs on the VPN different from the PE indicated by the Router ID field 302. In the example VPLS, VPN 101, the Other PE list field 324 for the record with Router ID value 1.1.1.1 (PE 120 a) and VC ID corresponding to VPN 101 holds data that indicates PE 120 b and PE 120 c.

According to a particular embodiment, a PE-Record attribute is added to the RADIUS attributes of RFC2865. The PE-Record attribute includes a first octet that indicates the type is a PE-Record, a second octet that indicate the length of the attribute, and length-2 octets that hold text that indicates the value of the PE-Record. The text is composed of two or three colon separated parts: a PE-Router-ID attribute (as described above); an attachment individual identifier (AII), and an optional list of pairs. The contents of the PE-Router attribute in the text of the PE-Record indicate a target provider edge node for a pseudo wire on the VPN of interest. The contents of the AII identify a particular attachment circuit on the target provider edge node. Any AII that is unique on the edge node indicated by the data in the PE-Router-ID may be used. Each pair in the optional list of pairs includes an attribute name and a value of attribute for a pseudo wire between the provider edge node identified in field 302 and the target provider edge node of the current PE-Record attribute. In some embodiments, the elements of each pair are separated by equals signs. For example, a per-hop-behavior value of 256 is indicated by the pair “PHB=256.” It is assumed for purpose of illustration that PW 140 a from source edge node 120 a to target edge node 120 c is switched to attachment circuit 122 k that is identified on edge node 120 c (IP address 1.1.1.3) as AII=“2”. In this illustration, an example PE-Record attribute for PW 140 a is given by the octets Z.16.X.6.1.1.1.3.2.PHB=256, where the octet value “Z” indicates the type is a PE-Record, and “X” indicates the type is PE-Router-ID, as described above, and the octet value “16” indicates that there are 16 octets in this PE-Record.

In some embodiments, the Other PE List field 324 holds one or more of the RADIUS PE-Record attributes. The VC indicated in the VC ID field 306 includes one or more pseudo wires from a source provider edge node indicated in the Router ID field 302 and each target edge node included in the Other PE List 324.

According to a particular embodiment, an Attachment-Individual-ID attribute is added to the RADIUS attributes of RFC2865. The Attachment-Individual-ID attribute includes a first octet that indicates the type is an Attachment-Individual-ID, a second octet that indicate the length of the attribute, and a length-2 octet value that indicates the value, e.g., “2.” For example, the value of Attachment-Individual-ID for attachment circuit 122 j is given by the three octets “A.3.2,” where the octet value “A” indicates the type is an Attachment-Individual-ID and is assigned by agreement of the RADIUS protocol authority or as a vendor-specific attribute. In some embodiments the Attachment-Individual-ID is used in the PE-Record. For example, the PE-Record attribute described above takes the form “Z.18.X.6.1.1.1.3.A.3.2.PHB=256” when the Attachment-Individual-ID attribute is used to describe the AII.

According to a particular embodiment, a Per-Hop-Behavior attribute is added to the RADIUS attributes of RFC2865. The Per-Hop-Behavior attribute includes a first octet that indicates the type is Per-Hop-Behavior, a second octet that indicate the length of the attribute is 6, and four-octet value. The first two octets indicate the Per-Hop-Behavior value as described in RFC3140, the entire contents of which are hereby incorporated by references as if fully set forth herein. For example, the value of Per-Hop-Behavior for attachment circuit 22 j is given by the six octets “B.6.256,” where the octet value “B” indicates the type is a Per-Hop-Behavior and is assigned by agreement of the RADIUS protocol authority or as a vendor-specific attribute. In some embodiments the Per-Hop-Behavior is used in the PE-Record. For example, the PE-Record attribute described above takes the form “Z.17.X.6.1.1.1.3.A.3.2.B.6.256” when the Attachment-Individual-ID attribute is used to describe the AII.

FIG. 3C is a block diagram that illustrates a pseudo wire record 340 on a provisioning server, according to an embodiment. In the illustrated embodiment, the record 340 includes three fields, a Router ID field 302, an Other PE ID field 344, and a pseudo wire (PW) properties field 348.

The Router ID field 302 is as described above for both the attachment circuit record 300 and VPN record 320. The Router ID field 302 serves as a primary index to a particular PW record 340 in the data stored on the RADIUS server.

The Other PE ID field 344 holds data that indicates a target provider edge node for a particular pseudo wire. The Other PE ID field 344 serves as a secondary index to a particular PW record 340 in the data stored on the RADIUS server. In some embodiments, the field 344 includes just an identifier for the router. In some embodiments the field 344 includes also an identifier for a particular attachment circuit on the target router.

The PW properties field 348 holds data that indicate one or more properties of the PW that are used to configure a provider edge node to form the PW. For example, in some embodiments, the PW properties field includes data that indicates a control plane protocol (e.g., LDP) for negotiating the PW with the target provider edge node. In some embodiments, the PW properties field includes data that indicates a value of an EXP parameter (e.g., a hexadecimal value “3” designated “0x03”) as described in RFC3032, cited above. In some embodiments, the PW properties field 348 includes one or more pairs of attributes and values as described above for the PE-Record attribute. In some embodiments, the PW properties field 348 holds data that indicates a level of service. e.g., 1, 2, 3 for gold, silber, bronz, respectively.

In some embodiments, the Other PE ID field 324 and PW properties field 348 are included in one RADIUS PE-Record attribute, in which the attribute-value pairs are not optional. For example, the PE-Router-ID and AII in the text octets of the PE-Record attribute form the Other PE ID field 344. The attribute-value pairs in the text octets of the PE-Record attribute form the PW Properties field 348.

An advantage of the data structures described above with reference to FIG. 3A, FIG. 3B and FIG. 3C, is that they allow the hierarchical relationships between attachment circuits, VPN edge node members and pseudo wires to be represented as flat files used by the RADIUS server. As described below, the configuration data stored in these data structures may be pushed to a provider edge node in one or multiple different messages. Another advantage of these data structures are that they are small and thus can be used to send incremental changes in configuration data to provider edge nodes.

In some embodiments, configuration data for one or more of these data structures, or their equivalents, are stored on different servers, including servers that are not RADIUS servers.

In another embodiment, data for two or more of these data structures are combined into the same data structure on the RADIUS or other server. An advantage of combining these data structures is that fewer operations are required on the server, including the RADIUS server, to retrieve the configuration data. Thus the combined data can be returned in one transaction without modifying the RADIUS server methods. A disadvantage of combining these data structures is that data not relevant to a particular edge node is included in a record and retrieved. Thus, either the server or the receiving provider edge node consumes processing resources to filter out the unwanted information. If the receiving node does the filtering, then extra network resources are consumed to transmit the excess data.

FIG. 3D is a block diagram that illustrates a combined VPN record 360 on a provisioning server, according to an embodiment. In the illustrated embodiment, the record 360 includes a VC ID field 306 and a list 362 of attachment circuit connection records. The VC ID field 306, as described above, holds data that indicates a VPN identifier from a customer's perspective. Thus VC ID field 306 indicates all the pseudo wires in both VPLS and VPWS VPNs. The list 362 of attachment circuit connection records includes attachment circuit connection records 370 a, 370 b and other attachment circuit connection records indicated by ellipsis 371 (collectively referenced herein as connection records 370).

Each connection record 370 uniquely identifies a source attachment circuit using a PE ID field 372 a, 272 b (and others, collectively referenced herein as PE ID fields 372) and an AC ID field 374 a, 274 b (and others, collectively referenced herein as AC ID fields 374). Any method may be used to identify the PE and AC. In some embodiments, the PE ID field 372 holds the RADIUS PE-Router-ID attribute, defined above; and the AC ID field 374 holds the RADIUS Attachment-Individual-ID attribute, also defined above.

Each connection record also includes an import type field 376 a, 376 b (and others, collectively referenced herein as import type field 376) and an export type field 378 a, 378 b (and others, collectively referenced herein as export type field 378). The import type field 376 and export type field 378 hold data that indicate to which remote provider edge node a particular attachment circuit should connect when that attachment circuit is the source. The type data in fields 376, 378 indicate that the associated attachment circuit is either a hub or a spoke in the VPN topology. As is well known in the art for BGP, a provider edge node functioning as a hub terminates multiple pseudo wires for a given VPN. For each remote provider edge participating in the VPN, there is exactly one pseudo wire between the hub provider edge and the remote provider edge. A provider edge functioning as a Spoke terminates exactly one pseudo wire to a remote hub provider edge for a given VPN. Import and export roles define whether a provider edge functions as a hub or a spoke and, as such, with what remote provider edges it must establish pseudo wires in order to build the L2VPN. In a hub and spoke environment, there must be only one Hub for any given VPN and the rest of the provider edges must be spokes. In a full-mesh environment, every provider edge operates as a hub.

It is assumed for purposes of illustration that the values in the fields of connection records for an example VPWS VPN are given in Table 1. TABLE 1 Values of fields in an example list of attachment circuit connections record # PE ID AC ID Import Export 1 PE 120a AC 122b spoke hub1 2 PE 120a AC 122c spoke hub2 3 PE 120b AC 122h hub1 spoke 4 PE 120c AC 122j hub2 spoke

When the configuration data of Table 1 is pushed to PE 120 c to configure AC 122 j, record # 4 indicates that AC 122 j imports from a hub and exports to a spoke. To differentiate different source attachment circuits on the same PE from which AC 122 j imports, hubs are distinguished by a suffix number. Thus AC 122 j imports from hub2. In embodiments such as VPLS, where this distinction is not needed, the suffix number is omitted. To configure the switching of AC 122 j, the other records depicted in Table 1 are inspected and those that do not export a hub2 are filtered out. Thus records #1 and #3 are filtered out, which leaves record #2 for AC 122 c on PE 120 a. Thus a PW is indicated that extends from AC 122 j on PE 120 c to AC 122 c on PE 120 a. Without the suffixes, a PW would also be established from AC 122 j on PE 120 c to AC 122 b on PE 120 a.

The data in the combined VPN record does not give PW properties. Thus, some additional data, such as PW records 340, is useful.

The combined VPN record 360 is most useful in VPLS where the topologies are almost exclusively “full-mesh” or “hub-and-spoke”. When applying the combined VPN record 360 to VPWS, the topologies are typically not symmetric. As a result, each pseudo wire mapping must be defined as a separate “Hub” service. For example, the AC 122 k, PE 120 c to PE 120 a, AC 122 a connection may be described as “hubA”. A different hub name must be applied to each AC-PE-PE-AC pseudo wire mapping service in the VPWS domain.

A method for provisioning a virtual private network at a RADIUS server is a particular embodiment of method 200. In an illustrated embodiment using data structures 300, 320, 340, three levels of authorization are supported, using three different types of set commands to index into the three record types. A primary index is based on a router identifier for the provider edge node to be configured. A secondary index is based on the contents of the RADIUS username attribute.

In step 210, configuration data is received and stored on a RADIUS server. For example, configuration data is received and stored in one or more of the data structures described above with reference to FIGS. 3A, 3B, 3C, 3D, using any of the methods described above with reference to step 210.

In a particular embodiment of step 222, a RADIUS change of authorization request (similar to a SNMP set command) understood by a RADIUS server according to a recent extension of RADIUS described in RFC 3576) is received at the RADIUS server. The set command includes a type field, the contents of which indicate the type of response that is appropriate. In an illustrated embodiment, the set command is received from a process that determines a change has been made to the definition of a level of service associated with one or more pseudo wires on one or more VPNs. The set command includes a router ID of the provider edge node to receive the configuration data. In the illustrated embodiment, the set command also includes an identifier for one or more attachment circuits. For purposes of illustration, it is assumed that the IP address of PE 120 a is included in the set command.

For purposes of illustration it is assumed that in a first example embodiment, the RADIUS set command type field holds data that indicates a CE NAI for a VPLS, e.g., “providerX/atlantia@vpnY.domainZ.net.” For purposes of illustration it is further assumed that in a second example embodiment, the RADIUS set command type field holds data that indicates an AC ID on PE 120 a for a VPWS, e.g., “ATM14.0.1.” These two examples correspond to attachment circuit authorization.

In a particular embodiment of step 232, it is determined whether the set command type indicates an attachment circuit. In an illustrated embodiment, the contents of the set command type field indicates an attachment circuit if those contents match the contents of an AC ID field 304 in a CE-AC attachment record 300 for the sending NAS. If it is determined that the set command type field holds data that indicates an attachment circuit, then control passes to step 240, to push configuration data for that attachment circuit to the provider edge node indicated in the set command. If not, then control stays in step 232 to determine whether the set command type field indicates a VC ID for a collection of one or more pseudo wires.

It is assumed for purposes of illustration that, in the first example of the illustrated embodiment, it is determined in step 232 that the set command type field “providerX/atlantia@vpnY.domainZ.net” matches a value in an AC ID field 304 of a particular record 300 for PE 120 a, which has the IP address 1.1.1.1 in the router ID field 302. It is further assumed for purposes of illustration that, in the second example of the illustrated embodiment, it is determined in step 232 that the contents of the set command type field “ATM14.0.1” matches a value in an AC ID field 304 of a particular record 300 for PE 120 a, which has the IP address 1.1.1.1 in the router ID field 302. In both examples, control then passes to step 240 to push configuration data for that particular attachment circuit.

In a particular embodiment of step 240, a RADIUS change of authorization request message is pushed to the indicated provider edge node (e.g., PE 120 a) based on the set command. For this step, the provisioning server 130 acts as a RADIUS client which sends the request and the PE 120 acts as a RADIUS server. Thus the RADIUS server acting as provisioning server 130 is modified to include a RADIUS client that can generate the change of authorization request. The automated configuration process on the PE 120 includes, as a sub-process, a RADIUS server to receive and store the configuration data in the request.

The RADIUS change of authorization request includes data that indicates the contents of the VC ID field 306 and AC Service field 308, if any, of the record 300 that matches the router ID field 302 and AC ID field 304. It is assumed for purposes of illustration that, in the first example of the illustrated embodiment, for the associated record 300 with Router ID 1.1.1.1 and AC ID “providerX/atlantia@vpnY.domainZ.net”, the contents of the VC ID field 306 indicate the collection of PWs 104 a, 104 c, 104 e that make up VPN 101. It is further assumed for purposes of illustration that, in the second example of the illustrated embodiment, for the associated record 300 with Router ID 1.1.1.1 and AC ID “ATM14.0.1”, the contents of the VC ID field 306 indicate the single PW 104 a. In some embodiments, the VC ID is designated in the change of authorization request as the RADIUS VPN-ID attribute or the RADIUS Router-Distinguisher attribute, as can be determined by the RADIUS attribute type.

In some embodiments in which VC authorization, VPN authorization and PW authorization are performed separately, control passes from step 240 back to step 222 to receive a different message before sending additional data to the provider edge node being configured (e.g., server 120 a). In some embodiments, one or more of the additional messages are sent by the edge node to be configured. In some embodiments, the additional messages are all sent by a process on one or more different nodes in network 110 from the provider edge node being configured. In some embodiments, the additional messages are all directed to the RADIUS server. In some embodiments, one or more of the additional messages are sent to servers using different protocols.

In some embodiments, step 240 automatically includes, in the same or different RADIUS change of authorization request, data that indicates target edge nodes associated with the VC ID. For example, step 240 includes pushing configuration data that indicates the contents of the Other PE list 324 of the record 320 that matches the router ID field 302 and VC ID field 306. It is assumed for purposes of illustration that, in a third example of the illustrated embodiment, for the associated record 320 with Router ID 1.1.1.1 and VC ID for VPN 101, the contents of the Other PE list 324 indicate the collection of target PEs, 120 b, 120 c. It is further assumed for purposes of illustration that, in a fourth example of the illustrated embodiment, for the associated record 320 with Router ID 1.1.1.1 and VC ID for 140 a, the contents of the Other PE list 324 indicate the single target PE 120 c of PW 104 a. In some embodiments, the Other PE list is designated in the pushed message as the RADIUS PE-record attribute, as can be determined by the RADIUS attribute type.

If separate change of authorization requests are sent, it is determined in an embodiment of step 232 whether the change of authorization request type field indicates a VC ID for a collection of one or more pseudo wires. In an illustrated embodiment, the contents of the change of authorization request type field indicates a VC ID if those contents match the contents of a VC ID field 306 in a VPN record 320 for the provider edge node to be configured. If it is determined that the change of authorization request type field holds data that indicates the VC ID, then control passes to step 240 to push configuration data that indicates the contents of the Other PE list 324 of the record 320 that matches the router ID field 302 and VC ID field 306, as described above. In some embodiments, the VC ID is designated in the change of authorization request type field as the RADIUS VPN-ID attribute or the RADIUS Router-Distinguisher attribute, as can be determined by the RADIUS attribute type. If the change of authorization request does not include a VC ID, then control passes to step 235 to determine whether the user name indicates a particular target edge node to which a pseudo wire is to be formed.

In some embodiments, step 240 automatically includes, in the same or different RADIUS change of authorization request, data that indicates pseudo wire properties associated with the PW (e.g., PW 140 a) to the target PE (e.g., 120 c). The RADIUS change of authorization request includes data that indicates the contents of the PW properties field 348 of the PW record 340 that matches the router ID field 302 and Other PE id field 344. It is assumed for purposes of illustration that, in a fifth example of the illustrated embodiment, for the associated record 340 with Router ID 1.1.1.1 and Other PE ID for 120 c, the contents of the PW properties field 348 indicate the level of service for each hop along PW140 a. Similarly, for the associated record 340 with Router ID 1.1.1.1 and Other PE ID for 120 c, the contents of the PW properties field 348 indicate the level of service for each hop along PW 140 a. In some embodiments, the PW properties are designated in the response message as the RADIUS PE-record attribute or the new RADIUS Per-Hop-Behavior attribute, as can be determined by the RADIUS attribute type.

If separate change of authorization requests are sent, it is determined in an embodiment of step 232 whether the change of authorization request type field indicates a PE ID for a target of a pseudo wire. In an illustrated embodiment, the contents of the change of authorization request type field indicates a PE ID if those contents match the contents of a Other PE ID field 306 in a PW record 340 for the provider edge node to be configured. If it is determined that the change of authorization request holds data that indicates the Other PE ID, then control passes to step 240, to push configuration data to the provider edge node. If not, then control passes to continue processing some other RADIUS function indicated in the change of authorization request. If no match is found for a PE 120 with any change of authorization request type in the RADIUS database during step 232, then a RADIUS change of authorization request is not sent to that PE 120. In some embodiments, the Other PE ID field is designated in the change of authorization request as the new RADIUS PE-router-ID attribute, as can be determined by the RADIUS attribute type

It is noted, that the order described above is changed in different embodiments. For example, in some embodiments, RADIUS change of authorization requests are first sent in step 240 that include data for provisioning one or more pseudo wires before an association is made between the pseudo wire and one or more attachment circuits.

4.0 Implementation Mechanisms—Hardware Overview

FIG. 4 is a block diagram that illustrates a computer system 400 upon which an embodiment of the invention may be implemented. The preferred embodiment is implemented using one or more computer programs running on a network element such as a router device. Thus, in this embodiment, the computer system 400 is a router.

Computer system 400 includes a communication mechanism such as a bus 410 for passing information between other internal and external components of the computer system 400. Information is represented as physical signals of a measurable phenomenon, typically electric voltages, but including, in other embodiments, such phenomena as magnetic, electromagnetic, pressure, chemical, molecular atomic and quantum interactions. For example, north and south magnetic fields, or a zero and non-zero electric voltage, represent two states (0,1 w) of a binary digit (bit). A sequence of binary digits constitutes digital data that is used to represent a number or code for a character. A bus 410 includes many parallel conductors of information so that information is transferred quickly among devices coupled to the bus 410. One or more processors 402 for processing information are coupled with the bus 410. A processor 402 performs a set of operations on information. The set of operations include bringing information in from the bus 410 and placing information on the bus 410. The set of operations also typically include comparing two or more units of information, shifting positions of units of information, and combining two or more units of information, such as by addition or multiplication. A sequence of operations to be executed by the processor 402 constitutes computer instructions.

Computer system 400 also includes a memory 404 coupled to bus 410. The memory 404, such as a random access memory (RAM) or other dynamic storage device, stores information including computer instructions. Dynamic memory allows information stored therein to be changed by the computer system 400. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The memory 404 is also used by the processor 402 to store temporary values during execution of computer instructions. The computer system 400 also includes a read only memory (ROM) 406 or other static storage device coupled to the bus 410 for storing static information, including instructions, that is not changed by the computer system 400. Also coupled to bus 410 is a non-volatile (persistent) storage device 408, such as a magnetic disk or optical disk, for storing information, including instructions, that persists even when the computer system 400 is turned off or otherwise loses power.

The term computer-readable medium is used herein to refer to any medium that participates in providing information to processor 402, including instructions for execution. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 408. Volatile media include, for example, dynamic memory 404. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves. Signals that are transmitted over transmission media are herein called carrier waves.

Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, a magnetic tape or any other magnetic medium, a compact disk ROM (CD-ROM), a digital video disk (DVD) or any other optical medium, punch cards, paper tape, or any other physical medium with patterns of holes, a RAM, a programmable ROM (PROM), an erasable PROM (EPROM), a FLASH-EPROM, or any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.

Information, including instructions, is provided to the bus 410 for use by the processor from an external terminal 412, such as a terminal with a keyboard containing alphanumeric keys operated by a human user, or a sensor. A sensor detects conditions in its vicinity and transforms those detections into signals compatible with the signals used to represent information in computer system 400. Other external components of terminal 412 coupled to bus 410, used primarily for interacting with humans, include a display device, such as a cathode ray tube (CRT) or a liquid crystal display (LCD) or a plasma screen, for presenting images, and a pointing device, such as a mouse or a trackball or cursor direction keys, for controlling a position of a small cursor image presented on the display and issuing commands associated with graphical elements presented on the display of terminal 412. In some embodiments, terminal 412 is omitted.

Computer system 400 also includes one or more instances of a communications interface 470 coupled to bus 410. Communication interface 470 provides a two-way communication coupling to a variety of external devices that operate with their own processors, such as printers, scanners, external disks, and terminal 412. Firmware or software running in the computer system 400 provides a terminal interface or character-based command interface so that external commands can be given to the computer system. For example, communication interface 470 may be a parallel port or a serial port such as an RS-232 or RS-422 interface, or a universal serial bus (USB) port on a personal computer. In some embodiments, communications interface 470 is an integrated services digital network (ISDN) card or a digital subscriber line (DSL) card or a telephone modem that provides an information communication connection to a corresponding type of telephone line. In some embodiments, a communication interface 470 is a cable modem that converts signals on bus 410 into signals for a communication connection over a coaxial cable or into optical signals for a communication connection over a fiber optic cable. As another example, communications interface 470 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN, such as Ethernet. Wireless links may also be implemented. For wireless links, the communications interface 470 sends and receives electrical, acoustic or electromagnetic signals, including infrared and optical signals, which carry information streams, such as digital data. Such signals are examples of carrier waves

In the illustrated embodiment, special purpose hardware, such as an application specific integrated circuit (IC) 420, is coupled to bus 410. The special purpose hardware is configured to perform operations not performed by processor 402 quickly enough for special purposes. Examples of application specific ICs include graphics accelerator cards for generating images for display, cryptographic boards for encrypting and decrypting messages sent over a network, speech recognition, and interfaces to special external devices, such as robotic arms and medical scanning equipment that repeatedly perform some complex sequence of operations that are more efficiently implemented in hardware.

In the illustrated computer used as a router, the computer system 400 includes switching system 430 as special purpose hardware for switching information for flow over a network. Switching system 430 typically includes multiple communications interfaces, such as communications interface 470, for coupling to multiple other devices. In general, each coupling is with a network link 432 that is connected to another device in or attached to a network, such as local network 480 in the illustrated embodiment, to which a variety of external devices with their own processors are connected. In some embodiments an input interface or an output interface or both are linked to each of one or more external network elements. Although three network links 432 a, 432 b, 432 c are included in network links 432 in the illustrated embodiment, in other embodiments, more or fewer links are connected to switching system 430. Network links 432 typically provides information communication through one or more networks to other devices that use or process the information. For example, network link 432 b may provide a connection through local network 480 to a host computer 482 or to equipment 484 operated by an Internet Service Provider (ISP). ISP equipment 484 in turn provides data communication services through the public, world-wide packet-switching communication network of networks now commonly referred to as the Internet 490. A computer called a server 492 connected to the Internet provides a service in response to information received over the Internet. For example, server 492 provides routing information for use with switching system 430.

The switching system 430 includes logic and circuitry configured to perform switching functions associated with passing information among elements of network 480, including passing information received along one network link, e.g. 432 a, as output on the same or different network link, e.g., 432 c. The switching system 430 switches information traffic arriving on an input interface to an output interface according to pre-determined protocols and conventions that are well known. In some embodiments, switching system 430 includes its own processor and memory to perform some of the switching functions in software. In some embodiments, switching system 430 relies on processor 402, memory 404, ROM 406, storage 408, or some combination, to perform one or more switching functions in software. For example, switching system 430, in cooperation with processor 404 implementing a particular protocol, can determine a destination of a packet of data arriving on input interface on link 432 a and send it to the correct destination using output interface on link 432 c. The destinations may include host 482, server 492, other terminal devices connected to local network 480 or Internet 490, or other routing and switching devices in local network 480 or Internet 490.

The invention is related to the use of computer system 400 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system 400 in response to processor 402 executing one or more sequences of one or more instructions contained in memory 404. Such instructions, also called software and program code, may be read into memory 404 from another computer-readable medium such as storage device 408. Execution of the sequences of instructions contained in memory 404 causes processor 402 to perform the method steps described herein. In alternative embodiments, hardware, such as application specific integrated circuit 420 and circuits in switching system 430, may be used in place of or in combination with software to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

The signals transmitted over network link 432 and other networks through communications interfaces such as interface 470, which carry information to and from computer system 400, are exemplary forms of carrier waves. Computer system 400 can send and receive information, including program code, through the networks 480, 490 among others, through network links 432 and communications interfaces such as interface 470. In an example using the Internet 490, a server 492 transmits program code for a particular application, requested by a message sent from computer 400, through Internet 490, ISP equipment 484, local network 480 and network link 432 b through communications interface in switching system 430. The received code may be executed by processor 402 or switching system 430 as it is received, or may be stored in storage device 408 or other non-volatile storage for later execution, or both. In this manner, computer system 400 may obtain application program code in the form of a carrier wave.

Various forms of computer readable media may be involved in carrying one or more sequence of instructions or data or both to processor 402 for execution. For example, instructions and data may initially be carried on a magnetic disk of a remote computer such as host 482. The remote computer loads the instructions and data into its dynamic memory and sends the instructions and data over a telephone line using a modem. A modem local to the computer system 400 receives the instructions and data on a telephone line and uses an infra-red transmitter to convert the instructions and data to an infra-red signal, a carrier wave serving as the network link 432 b. An infrared detector serving as communications interface in switching system 430 receives the instructions and data carried in the infrared signal and places information representing the instructions and data onto bus 410. Bus 410 carries the information to memory 404 from which processor 402 retrieves and executes the instructions using some of the data sent with the instructions. The instructions and data received in memory 404 may optionally be stored on storage device 408, either before or after execution by the processor 402 or switching system 430.

3.0 Extensions and Alternatives

In this specification and Appendix, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

1. A method for configuring a network interface on an intermediate network node at an edge of a provider network to support a virtual private network, comprising the steps of: storing configuration data at a server on a host computer on a provider network, determining without human intervention whether conditions are satisfied for sending the configuration data to a particular node at an edge of the provider network without receiving a request message from the particular node; and if it is determined that conditions are satisfied for sending the configuration data, then sending the configuration data to the particular node to cause the particular node to configure a particular interface without human intervention for a particular virtual private network over the provider network based on the configuration data, wherein: the provider network is a packet-switched network; the particular virtual private network is a link layer virtual private network; the particular node is different from the host; and the particular interface is for a direct communication link to a customer network node outside the provider network.
 2. A method as recited in claim 1, wherein the particular interface is a virtual circuit of a plurality of virtual circuits on the same physical circuit.
 3. A method as recited in claim 1, wherein the particular interface is a physical circuit.
 4. A method as recited in claim 1, wherein the configuration data sent to the particular node is less than all configuration data for provisioning all interfaces on the particular node.
 5. A method as recited in claim 1, said step of determining whether conditions are satisfied for sending the configuration data further comprising determining whether a change is made to a parameter that describes a level of service on a tunnel from the particular node to another edge node at an edge of the provider network.
 6. A method as recited in claim 1, said step of determining whether conditions are satisfied for sending the configuration data further comprising determining whether a different edge node at an edge of the provider network, which is different from the particular node, has been added or removed from the particular virtual private network.
 7. A method as recited in claim 1, said step of determining whether conditions are satisfied for sending the configuration data further comprising determining whether a simple network management protocol (SNMP) set command is received at the server.
 8. A method as recited in claim 1, wherein the server is a Remote Authentication Dial In User Service (RADIUS) Server.
 9. A method as recited in claim 8, said step of sending the configuration data further comprises sending a RADIUS change of authorization request that includes a RADIUS attribute for a virtual private network identification that indicates the particular virtual private network on the provider network.
 10. A method as recited in claim 8, said step of sending the configuration data further comprises sending a RADIUS change of authorization request that includes a RADIUS attribute for an attachment identification that indicates both an identification for the particular virtual private network to which the particular interface belongs and an interface identification that uniquely indicates the particular interface among interfaces that belong to the particular virtual private network.
 11. A method as recited in claim 8, wherein the configuration data includes a RADIUS attribute for a different node on the edge of the provider network that is different from the particular node and that is included in the particular virtual private network.
 12. A method as recited in claim 8, wherein the configuration data includes a RADIUS attribute for a tunnel from the particular node to a different node on the edge of the provider network.
 13. A method as recited in claim 1, wherein the server is a Simple Network Management Protocol (SNMP) Server.
 14. An apparatus for configuring a network interface on an intermediate network node at an edge of a provider network to support a virtual private network, comprising the steps of: means for storing configuration data at a server on a host computer on a provider network, means for determining without human intervention whether conditions are satisfied for sending the configuration data to a particular node at an edge of the provider network without receiving a request message from the particular node; and means for sending the configuration data to the particular node to cause the particular node to configure a particular interface without human intervention for a particular virtual private network over the provider network based on the configuration data, if it is determined that conditions are satisfied for sending the configuration data, wherein: the provider network is a packet-switched network; the particular virtual private network is a link layer virtual private network; the particular node is different from the host; and the particular interface is for a direct communication link to a customer network node outside the provider network.
 15. An apparatus for configuring a network interface on an intermediate network node at an edge of a provider network to support a virtual private network, comprising: a network interface that is coupled to a provider network for communicating therewith a data packet; one or more processors; a computer-readable medium; and one or more sequences of instructions stored in the computer-readable medium, which, when executed by the one or more processors, causes the one or more processors to carry out the step of: storing configuration data on the computer-readable medium; determining without human intervention whether conditions are satisfied for sending the configuration data to a particular node at an edge of the provider network without receiving a request message from the particular node; and if it is determined that conditions are satisfied for sending the configuration data, then sending the configuration data to the different node to cause the different node to configure a particular interface without human intervention for a particular virtual private network over the provider network based on the configuration data, wherein: the provider network is a packet-switched network; the particular virtual private network is a link layer virtual private network; and the particular interface is for a direct communication link to a customer network node outside the provider network.
 16. An apparatus as recited in claim 15, wherein the particular interface is a virtual circuit of a plurality of virtual circuits on the same physical circuit.
 17. An apparatus as recited in claim 15, wherein the particular interface is a physical circuit.
 18. An apparatus as recited in claim 15, wherein the configuration data sent to the particular node is less than all configuration data for provisioning all interfaces on the particular node.
 19. An apparatus as recited in claim 15, said step of determining whether conditions are satisfied for sending the configuration data further comprising determining whether a change is made to a parameter that describes a level of service on a tunnel from the particular node to another edge node at an edge of the provider network.
 20. An apparatus as recited in claim 15, said step of determining whether conditions are satisfied for sending the configuration data further comprising determining whether a different edge node at an edge of the provider network, which is different from the particular node, has been added to the particular virtual private network or removed from the particular virtual private network.
 21. An apparatus as recited in claim 15, said step of determining whether conditions are satisfied for sending the configuration data further comprising determining whether a simple network management protocol (SNMP) set command is received.
 22. An apparatus as recited in claim 15, wherein execution of the one or more sequences of instructions further causes the one or more processors to performs functions of a Remote Authentication Dial In User Service (RADIUS) Server.
 23. An apparatus as recited in claim 22, said step of sending the configuration data further comprises sending a RADIUS change of authorization request that includes a RADIUS attribute for a virtual private network identification that indicates the particular virtual private network on the provider network.
 24. An apparatus as recited in claim 22, said step of sending the configuration data further comprises sending a RADIUS change of authorization request that includes a RADIUS attribute for an attachment identification that indicates both an identification for the particular virtual private network to which the particular interface belongs and an interface identification that uniquely indicates the particular interface among interfaces that belong to the particular virtual private network.
 25. An apparatus as recited in claim 22, wherein the configuration data includes a RADIUS attribute for a different node on the edge of the provider network that is different from the particular node and that is included in the particular virtual private network.
 26. An apparatus as recited in claim 22, wherein the configuration data includes a RADIUS attribute for a tunnel from the particular node to a different node on the edge of the provider network.
 27. An apparatus as recited in claim 15, wherein execution of the one or more sequences of instructions further causes the one or more processors to performs functions of a Simple Network Management Protocol (SNMP) Server. 